Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

Configuring Windows modules

A DataServer configuration that includes Windows can be a local configuration, where all the components run on the same machine, or a remote, client/server configuration. It can also include clients or servers running on different platforms. For example, a Windows client can access a DataServer running remotely on a UNIX host. See Table 5–1 for a list of the possible configurations for Windows. It describes what you must do to set up the client and server modules.

In a remote configuration, two DataServer modules run on the host even though you use only one executable:

Broker — The _probrkr executable starts the broker, which spawns the DataServer process.
DataServer — The broker spawns this process, so you do not interact with it directly. However, you must make sure that the broker uses the _orasrv DataServer executable.
Note: Only one broker can run in a directory at a time. If you want to run multiple brokers, run each in a separate directory.

The following sections explain how to configure and run the local DataServer and how to configure and run the DataServer modules in the Windows host machine. For instructions on setting up the client side of remote configurations on:

UNIX — See the "Configuring UNIX modules" section for information on the UNIX client.
Windows — See the "Configuring the local DataServer in Windows" section for information in the Windows client.